Distributed collaboration shifts the focus from a single central folder to an ecosystem of independent, peer-to-peer repositories. In this model, every repository—like my-git-repo and marys-repo—is a complete universe containing its own history and branch data.

1. Defining the "Remote"

Simply put, a remote repository is one that is not your own. It can exist on your company's network, the internet (GitHub), or even just another directory on your local filesystem. The defining trait is that it is a separate instance where work happens outside your immediate control.

2. Remotes as Bookmarks

Technically, a remote is just a shorthand alias or "bookmark." Instead of typing /Users/Mary/projects/marys-repo every time you want to check her progress, you map that path to a simple name like mary.

3. Independence of State

Repositories are linked but not synced automatically. Creating a remote bookmark doesn't move code; it only establishes the path for future data exchange via pushing or fetching.